-
Notifications
You must be signed in to change notification settings - Fork 696
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable offloading of literals by default #6246
Conversation
Signed-off-by: Eduardo Apolinario <[email protected]>
Code Review Agent Run #574bbeActionable Suggestions - 1
Review Details
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #6246 +/- ##
===========================================
- Coverage 50.51% 36.86% -13.65%
===========================================
Files 1162 1318 +156
Lines 91811 134703 +42892
===========================================
+ Hits 46375 49662 +3287
- Misses 41340 80714 +39374
- Partials 4096 4327 +231
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Changelist by BitoThis pull request implements the following key changes.
|
@@ -864,7 +864,7 @@ configmap: | |||
rate: 10 | |||
capacity: 100 | |||
literal-offloading-config: | |||
enabled: true | |||
enabled: false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider keeping literal-offloading-config.enabled
as true
since disabling it may impact large workflow execution performance. If this change is intentional, please provide context on why literal offloading is being disabled.
Code suggestion
Check the AI-generated fix before applying
enabled: false | |
enabled: true |
Code Review Run #574bbe
Is this a valid issue, or was it incorrectly flagged by the Agent?
- it was incorrectly flagged
Tracking issue
NA
Why are the changes needed?
We shipped offloading of literals by default in Flyte 1.14, but unfortunately given the limitations that feature currently exposes we feel that having that enabled by default is too disruptive, so instead, we're taking a more measured approach and once we feel the feature is ready for production we'll ship it by default.
A list of the limitations:
@dynamic
What changes were proposed in this pull request?
Set the flag to false in both single binary and flyte-core helm charts.
How was this patch tested?
Labels
Please add one or more of the following labels to categorize your PR:
This is important to improve the readability of release notes.
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link
Summary by Bito
This PR implements a significant change by disabling the literal offloading feature by default across all Flyte deployment configurations (AWS EKS, GCP, and sandbox). The change involves setting 'literalOffloadingConfigEnabled' to false in helm charts and removing related configurations from deployment manifests to address production environment limitations.Unit tests added: False
Estimated effort to review (1-5, lower is better): 3